x86: Do no thold cpu_add_remove_lock across stop_machine_run().
authorKeir Fraser <keir.fraser@citrix.com>
Fri, 14 May 2010 10:39:15 +0000 (11:39 +0100)
committerKeir Fraser <keir.fraser@citrix.com>
Fri, 14 May 2010 10:39:15 +0000 (11:39 +0100)
commit2a814aeaaf1e2fe258ab72fc60bb86b7ca4cb102
tree3bb398c9e2e984e80df50f50b292d12248ddcea6
parent5afdabbf824c995b6d66b4e69cd85c8948a3edb8
x86: Do no thold cpu_add_remove_lock across stop_machine_run().

Instead we protect against concurrent online/offline requests for a
single CPU asynchronously, using a cpumask for bookkeeping.

This means that cpu_add_remove_lock no longer needs to be acquired via
spin_trylock.

Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen/arch/x86/platform_hypercall.c
xen/arch/x86/smpboot.c